Tunisian Platform Compliance Analysis: Technical & Fiscal Specifications for Enterprise ERP & E-Commerce Systems (2024-2026 Regulatory Framework)
1. Executive Summary and Architectural Compliance Overview
This comprehensive research report serves as a technical and fiscal gap analysis for software platforms intending to operate within the Tunisian jurisdiction. The analysis is strictly grounded in the Code de la Taxe sur la Valeur Ajoutée (Code TVA), the Code de l'Impôt sur le Revenu des Personnes Physiques et de l'Impôt sur les Sociétés (Code IRPP/IS), and the critical electronic invoicing mandates introduced by the Finance Laws of 2023, 2024, and 2025.
The Tunisian fiscal landscape presents a unique, high-friction environment for international software platforms. Unlike standardized VAT jurisdictions (such as the EU VAT area), Tunisia employs a complex "Tax-on-Tax" calculation logic involving the Fonds de Développement de la Compétitivité (FODEC), a non-standard currency precision requiring three decimal places (millimes), and rigid, criminal-penalty-enforced requirements for sequential numbering and electronic signature homologation via Tunisie TradeNet (TTN). As the regulatory environment shifts towards mandatory B2B electronic invoicing starting July 2025 for specific tiers of enterprises, the platform's architecture must evolve from simple document generation to a state-based, cryptographically verifiable transaction ledger.1
This report dissects the platform's calculation logic against the "Tunisian Law Platform Calculation System" requirements. It identifies critical compliance gaps, particularly in the handling of the tax base definition, the immutable sequencing of fiscal documents, and the imminent interoperability requirements for the "El Fatora" system. The analysis indicates that a standard "global" ERP configuration will fail to meet Tunisian compliance standards, exposing the operator to significant fiscal penalties ranging from administrative fines to imprisonment for non-compliance with billing regulations.3
2. End-to-End Calculation Flow Analysis
The core of the compliance engine in the Tunisian context lies in the strict order of operations. The calculation stack is hierarchical and non-commutative; reversing any step—such as applying a discount after the tax calculation or calculating the tax before the application of para-fiscal charges like FODEC—constitutes a fiscal error. This error cascades through the accounting system, leading to incorrect declarations and potential accusations of tax evasion.
2.1 The Legal Calculation Pipeline
For a platform to be compliant, its calculation engine must execute the following linear pipeline for every transaction line item. This flow is immutable and must be reflected in the database persistence layer.
Phase 1: Pre-Tax Determination
The process begins with the Gross Unit Price (Prix Unitaire Brut - HT). This is the base price of the product or service before any modification. The first operation allowed is the Line Item Discount (Remise Ligne). Tunisian fiscal law recognizes commercial discounts (remises) as deductions from the base price before the calculation of VAT, provided they are shown on the invoice.4
Calculation: Net Unit Price = Gross Unit Price * (1 - Discount%)
Compliance Check: The discount must be applied to the unit price or the line total, but it must result in a "Montant Net HT" (Net Amount Excluding Tax).
Phase 2: The Para-Fiscal Inflation (FODEC)
This is a critical deviation from standard international logic. If the product belongs to a sector subject to the Fonds de Développement de la Compétitivité (FODEC)—typically industrial goods, specific manufacturing inputs, or regulated sectors—this fee is calculated on the Net Amount HT.
Calculation: FODEC Amount = Net Amount HT * 1% (or applicable sectoral rate).
Implication: The FODEC is not merely a tax collected in parallel; it inflates the base for the subsequent VAT calculation. Systems that calculate VAT on the Net HT and then add FODEC separately will under-calculate the VAT collected, leading to a deficiency in the Déclaration Mensuelle.5
Phase 3: The Tax Base Determination (Assiette TVA)
The "Assiette TVA" (VAT Base) is the sum of the Net Amount HT and all other taxes and fees associated with the sale, excluding the VAT itself.
Formula: TVA Base = Net Amount HT + FODEC Amount + (Droit de Consommation if applicable)
Insight: The inclusion of the Droit de Consommation (Consumption Duty) for luxury goods or specific imports further complicates this. If a product is subject to a 25% Consumption Duty, that duty is added to the HT, and the 19% VAT is calculated on the compound total. The platform must verify if the "TVA Base" field in the database is a computed column that dynamically aggregates these pre-tax charges.7
Phase 4: Value Added Tax (TVA)
The Value Added Tax is calculated on the derived Assiette TVA.
Formula: TVA Amount = TVA Base * Applicable Rate (7%, 13%, or 19%)
Rate Logic: The rate is determined by the intersection of the Product Category (e.g., IT equipment at 7%, standard goods at 19%) and the Customer's Fiscal Privileges (e.g., VAT Suspension Certificate holder at 0%). A robust system must query a "Tax Rule Engine" at this stage rather than relying on a static rate attached to the product.5
Phase 5: Final Aggregation and Fiscal Stamp
The final invoice total is the summation of all line items plus the Timbre Fiscal (Fiscal Stamp).
Formula: Total TTC = Sum(Line Net HT + Line FODEC + Line TVA) + Timbre Fiscal
Critical Detail: The Timbre Fiscal is a fixed duty (typically 1.000 TND for invoices > 1,000 TND TTC) added once per document. It is never subject to VAT and is added at the very end of the calculation flow.5
2.2 Data Flow Architecture and Precision
To support this stringent flow, the database schema for OrderLine and InvoiceLine must persist values with high precision. Standard floating-point arithmetic (IEEE 754) is insufficient due to the potential for rounding errors that accumulate over thousands of transactions.
Requirement: The platform must use Decimal(15,3) or Decimal(15,4) data types.
Persistence: It is mandatory to store the computed vat_base_3dec, fodec_amount_3dec, and vat_amount_3dec for every line. Relying on dynamic recalculation during audit (e.g., price * 1.19) is risky because tax rates or rules may change over time, and the historical invoice must remain effectively immutable.10
3. Product & Pricing Calculations: The Three-Decimal Imperative
The Tunisian currency system requires a fundamental adjustment to the "Price" object in any software architecture. The Tunisian Dinar (TND) is subdivided into 1,000 Millimes, requiring three decimal places for all financial displays and calculations. This impacts user interface design, database storage, and rounding logic.
3.1 Currency Precision and Display Logic
While many international platforms default to two decimal places (e.g., $10.99), a Tunisian invoice must display 10.990 DT. In industrial B2B contexts, unit prices often extend to four or five decimal places (e.g., 0.0455 DT per unit of raw material), but the final line extension must be rounded to three decimals.
Technical Constraint: The platform's frontend must be configured to force a minimum and maximum of three fraction digits for the currency locale fr-TN or ar-TN.
Database Migration: Legacy columns storing prices as Decimal(10,2) must be migrated to Decimal(15,3). Failure to do so results in "phantom pennies" where the sum of the lines does not equal the total due, a discrepancy that can trigger a rejection during a fiscal control.5
3.2 Rounding Strategies
The method of rounding is as critical as the precision. Tunisian fiscal accounting generally accepts Arithmetic Rounding (0-4 down, 5-9 up). However, the crucial decision is when to round.
Line-Level Rounding: Calculate tax for the line, round to 3 decimals, then sum. This is the preferred method for B2B invoicing as it ensures that the line item details on the printed invoice match the total exactly.
Document-Level Rounding: Sum all unrounded net amounts, calculate tax on the total, then round. This is sometimes used in B2C retail but can cause reconciliation issues if the invoice lists tax per line.
Gap Analysis: If the platform currently uses "Banker's Rounding" (Round Half to Even), it must be switched to Arithmetic Rounding to match Tunisian manual accounting practices.10
3.3 Unit Price Definition: HT vs. TTC
The system must allow the definition of Prix Unitaire HT (Price Excluding Tax). If the user inputs a Prix Unitaire TTC (Price Including Tax), the system must reverse-calculate the HT using the exact formula, accounting for both VAT and FODEC:
HT = TTC / (1 + TVA Rate + (FODEC Rate if applicable))
This reverse calculation often results in infinite decimals. The system must handle the rounding difference (the "penny gap") by storing a "rounding adjustment" field or by adjusting the last significant digit of the HT price to ensure the forward calculation HT * Tax returns to the exact TTC input.5
4. Discount System: Commercial vs. Financial Hierarchies
Tunisian commercial law and fiscal practice distinguish sharply between different types of price reductions. The platform's "Discount" field is insufficient; it must be split into distinct entities with different fiscal behaviors.
4.1 Remise, Rabais, and Ristourne (Commercial Reductions)
These are reductions linked to the nature of the sale (volume, quality, promotion) and are deducted from the Base Imposable (Tax Base).
Remise (Discount): Usually applied at the line level. It reduces the Net HT.
Rabais: Applied when goods are defective or non-conforming.
Ristourne (Rebate): Calculated on global turnover over a period (e.g., end-of-year volume rebate). This typically generates a Facture Avoir (Credit Note) rather than appearing on the initial invoice.
Platform Requirement: The calculation engine must deduct these before calculating FODEC or TVA. The invoice must visually demonstrate the Prix Brut, the Remise (%), and the Prix Net.4
4.2 Escompte (Financial Discount)
An Escompte is a reduction granted for early payment (e.g., "2% discount if paid within 10 days").
Fiscal Specificity: In Tunisia, if the financial discount is unconditional and shown on the invoice, it reduces the VAT base. However, if it is conditional (dependent on the client actually paying early), the VAT is initially charged on the full amount. If the client pays early, a credit note is issued for the difference.
Accounting Mapping: Unlike commercial discounts which disappear into the "Net Sales" account, financial discounts are often recorded in a specific financial expense account (Charge Financière - Compte 65). The platform needs to allow the user to configure whether a discount is "Commercial" or "Financial" to route it to the correct General Ledger account.4
4.3 Cascading Discounts
In B2B scenarios, multiple discounts may apply (e.g., "Partner Discount" + "Seasonal Promo"). The system must define if they are additive (10% + 5% = 15%) or cascading (Price * 0.90 * 0.95). Tunisian ERPs generally support cascading discounts. The "Base HT" for the second discount is the Net HT after the first discount. The platform must be transparent about this logic to avoid disputes between buyer and seller regarding the final price.
5. TVA & Fiscal Logic: The Multi-Rate Engine
This section details the complex tax engine logic required for Tunisia, specifically focusing on the multi-rate system, the handling of exemptions, and the critical concept of the "Fait Générateur."
5.1 TVA Rates and Product Classification
The platform must support a flexible, date-versioned tax table. As of the Finance Laws 2023-2025, the common rates are:
19%: Standard rate (goods, services, commercial rents).
13%: Reduced rate (architects, engineers, lawyers, low-voltage electricity, some petroleum products).
7%: Low rate (IT equipment, pharmaceutical inputs, education, transport, medical activities).
0%: Export or suspension regimes.
Logic Gap: A hardcoded tax rate on a product is a compliance risk. The rate is a function of the Product AND the Customer. For example, a laptop is typically 7%, but if sold to a Diplomatic Mission or a Total Exporter with a valid certificate, it becomes 0%.8
5.2 The "Suspension de TVA" Regime
Exporters and privileged companies (e.g., oil & gas, investment projects) operate under a "Suspension de TVA" certificate (Attestation d'Exonération).
Validation Logic: The system must allow a customer profile to store a certificate number (e.g., "N° 1234/2024"), a start date, and an end date.
Calculation Override: If the current order date falls within the validity period of the certificate, the TVA calculation is suppressed (Rate = 0%).
Mandatory Mention: The invoice MUST print the specific legal phrase: "Exonéré de TVA en vertu de l'attestation n° [Number] du délivrée par le bureau de contrôle des impôts de [City]." Failure to print this voids the exemption during an audit, making the seller liable for the unpaid tax.8
5.3 The "Fait Générateur" (Tax Point)
The most sophisticated aspect of Tunisian fiscal law is the determination of when the tax becomes due. This differs by transaction type:
Sale of Goods (Bien): The tax point is the Livraison (Delivery) of the merchandise. The issuance of a Delivery Note (Bon de Livraison) triggers the tax liability, even if the invoice is issued later or payment is delayed.16
Services (Prestation): The tax point is the Encaissement (Collection/Payment) of the price. Tax is due when the money hits the bank account.
State Contracts (Marchés Publics): For construction or supplies to the State, the tax point is often the Encaissement, regardless of delivery.
System Implication: The platform must distinguish between "Invoice Date" and "Tax Point Date." For goods, the accounting module must accrue the VAT liability upon the generation of the "Bon de Livraison," not just the invoice. For services, the system should ideally support "Cash Accounting" for VAT, reporting it only when payment is logged.18
5.4 Retenue à la Source (Withholding Tax)
In many B2B and State transactions, the buyer is required to withhold a percentage of the VAT (typically 25% or 100% depending on the status) and pay it directly to the Treasury.
Invoice Presentation: The invoice total remains the same, but the "Net Payable" by the client is reduced by the withheld amount. The client then provides a "Certificat de Retenue à la Source."
Configuration: The system must allow marking an invoice as "Subject to Withholding," calculating the withheld amount for reporting purposes, even though the Invoice Total TTC does not change.16
6. Cart, Quotation & Order Calculations: Pre-Fiscal States
6.1 State Transitions and Immutability
In compliance with rigid numbering rules, the platform must clearly distinguish between "Draft" documents and "Final" fiscal documents.
Cart/Quotation (Devis):
Calculations are provisional. No fiscal impact.
Validity: Must explicitly state a validity duration (e.g., 30 days) to protect the seller from inflation or tax rate changes.5
Order (Bon de Commande):
Represents a contractual agreement. Prices are locked.
Delivery Note (Bon de Livraison - BL):
Critical Fiscal Document: As established, the BL validates the "Livraison." In Tunisia, it is illegal to transport goods without a BL or Invoice. The BL must be numbered sequentially. The system must allow the conversion of multiple BLs into a single "Facture Récapitulative" at the end of the month, linking all BL numbers to the invoice.19
6.2 Validity of Price and Tax Rate Changes
If the VAT rate changes (e.g., via a new Finance Law on January 1st) between the Quotation date and the Delivery date, the Invoice must use the rate valid at the Fait Générateur (Delivery).
Scenario: A quote is accepted in December 2024 (VAT 19%). Delivery occurs in January 2025. If the law changes VAT to 20%, the invoice must reflect 20%. The platform's "Convert Quote to Order" logic must re-validate the tax rates against the delivery date.14
7. Invoice Logic (Virtual) & The 2025 Electronic Mandate
This module is currently undergoing a massive regulatory shift. The platform must support both the traditional requirements and the emerging "El Fatora" standards.
7.1 Mandatory Mentions (Mentions Obligatoires)
To avoid fines (100 to 3,000 TND per omission) and invalidation of the invoice, every generated document must contain 5:
Seller Identity: Full Reason Sociale, Registered Address, and the all-important Matricule Fiscal. Format: 1234567 X/Y/Z 000 (Matricule + Code TVA + Code Catégorie + Etb).
Buyer Identity: Name, Address, and Matricule Fiscal (Mandatory for B2B transactions).
Unique Sequential Number: The system must guarantee n, n+1 generation without gaps.
Dates: Issue Date.
Tax Breakdown: A summary table showing Base HT, Rate, and Amount for each VAT rate applied.
Timbre Fiscal: Explicitly listed.
7.2 Sequential Numbering and Immutability
The "No Delete" Rule: It is strictly forbidden to delete an invoice once finalized. If an error occurs, the user must issue a Facture Avoir (Credit Note) to cancel it. The platform must disable any "Delete" functionality for finalized invoices.
Gapless Series: The numbering must be continuous. The system can reset annually (e.g., 2025-0001) but cannot skip numbers. Separate series for different Point of Sales (POS) or branches are permitted (e.g., WEB-2025-001, SHOP-2025-001) as long as each series is distinct and continuous.11
7.3 Droit de Timbre (Fiscal Stamp)
Current Rule: A stamp duty of 1.000 TND is applied to invoices.
Threshold: According to recent updates, this is mandatory for invoices exceeding 1,000 TND TTC. For cash transactions, other rules may apply, but for a standard B2B platform, the 1 DT rule is paramount.
Exclusions: Invoices for export are exempt.
Placement: Added to the "Net à Payer," not the tax base. The system must have a configurable threshold setting to adapt to future Finance Law changes.5
7.4 Electronic Invoicing (El Fatora - 2025)
Starting July 2025, interoperability with the national El Fatora system (managed by TTN - Tunisie TradeNet) becomes mandatory for specific categories of enterprises.
The Mandate: Large enterprises and those in the DGE (Direction des Grandes Entreprises) are the first wave. The goal is to eliminate paper invoices for B2B.
Technical Spec:
Format: The invoice must be generated as a structured XML/JSON file complying with TTN specifications.
Digital Signature: The file must be signed using a DigiGo or ANCE-approved electronic certificate to guarantee authenticity and integrity.
QR Code: The visual PDF representation must include a QR code generated from the signature to allow offline verification.
Archiving: The platform must archive these signed files for 10 years in a way that preserves the signature's validity.
API Integration: The platform needs to connect to the TTN API to "register" the invoice and receive a unique token/hash, proving it has been declared.1
8. Accounting Module & General Ledger Integration
The platform acts as a subsidiary ledger. To be useful to a Tunisian enterprise, it must export data compliant with the Système Comptable des Entreprises (SCE).
8.1 Chart of Accounts (Plan Comptable) Mapping
The system must aggregate totals by tax rate for the accounting entry. A typical sales entry generated by the platform should look like this:
Account (Compte)
Description
Debit
Credit
411
Clients (Receivables)
Total TTC


707
Vente de Marchandises


Net HT
43671
TVA Collectée (19%)


Amount 19%
43672
TVA Collectée (7%)


Amount 7%
4365
FODEC à Payer


FODEC Amount
436x
Timbre Fiscal


1.000

8.2 Revenue Recognition Logic
Cut-off: Revenue is legally recognized at Delivery (Livraison). If the platform issues an invoice in January for goods delivered in December, the revenue (and VAT) belongs to December. The platform's accounting export must support "Date of Delivery" based filters to assist accountants in the "Cut-off" procedure.18
9. Risk Matrix and Sanctions
Failure to adhere to these calculation and procedural standards carries severe risks:

Violation
Sanction
Source
Non-Sequential Numbering
Rejection of accounting, Fines up to 5,000 TND
5
Missing Mandatory Mentions
Fine of 100 TND per invoice, max 5,000 TND
5
Deletion of Invoices
Considered Tax Fraud. Imprisonment 16 days to 3 years.
3
FODEC Miscalculation
Reassessment of VAT base + Penalties on arrears (0.5% per month)
6
Failure to E-Invoice (post-2025)
Fines per invoice, loss of VAT deduction right for the buyer
3

10. Recommendations for Implementation
Engine Decoupling: Do not hardcode "Tax = 19%". Implement a Tax Rule Engine where rules are Rate, BaseModifier (e.g., +FODEC), and Condition (e.g., Client!= Exempt).
Date Management: Ensure the "Tax Point Date" (Date d'exigibilité) is stored separately from "Invoice Creation Date." This is vital for the monthly Déclaration Mensuelle d'Impôts.
El Fatora Readiness: Begin integration with TTN's API sandbox immediately. The 2025 deadline is strict. The system must be able to generate the XML payload required by TTN and handle the "Homologation" response token.
Audit Trail: Log every state change of the invoice. Tunisian tax auditors (Contrôle Fiscal) look for gaps in sequence or modifications after finalization. A blockchain-style hash chain for the invoice table is a strong feature for proving integrity.
Conclusion
The "Tunisian Law Platform Calculation System" requires a fundamental shift from generic e-commerce logic. The pivotal requirements are the three-decimal precision, the FODEC-inclusive tax base, and the strict sequential immutability enforced by severe penalties. By implementing the architecture detailed above, the platform will not only ensure compliance with the Code TVA and the 2025 Electronic Invoicing mandate but also protect the end-users from fiscal risks associated with calculation errors.
Detailed Calculation Example (Reference Case)
Scenario: Selling an industrial machine to a non-exempt local company.
Product Price HT: 2,500.000 TND
Discount (Remise): 10%
FODEC: 1%
TVA: 19%
Step-by-Step Execution:
Gross Price: 2,500.000
Net Price: 2,500.000 * (1 - 0.10) = 2,250.000 TND
FODEC: 2,250.000 * 0.01 = 22.500 TND
TVA Base: 2,250.000 + 22.500 = 2,272.500 TND (Note: Tax is calculated on 2272.5, not 2250)
TVA Amount: 2,272.500 * 0.19 = 431.775 TND
Total TTC: 2,250.000 + 22.500 + 431.775 = 2,704.275 TND
Timbre Fiscal: TTC > 1000, so add 1.000 TND.
Net to Pay: 2,705.275 TND
Any deviation from this result (e.g., 2704.27 or 2705.28) indicates a compliance failure in the rounding or logic engine.
Works cited
Facturation Électronique en Tunisie 2025 : Le Guide Ultime pour les Entreprises | TEIF Manager by BTB LABS, accessed December 22, 2025, https://www.teif.tn/blog/ressources-actualites-2/facturation-electronique-en-tunisie-2025-le-guide-ultime-pour-les-entreprises-5
La facturation électronique en Tunisie à partir du 1er juillet, accessed December 22, 2025, https://facture-tunisie.com/412/fr/39/reglementations/la-facturation-electronique-en-tunisie-a-partir-du-1er-juillet
Facturation électronique : Les sanctions applicables à partir du 1er juillet 2025 - Turess, accessed December 22, 2025, https://www.turess.com/fr/numerique/1011591
Mentions obligatoires sur une facture : la liste complète - Dext, accessed December 22, 2025, https://dext.com/fr/ressources/blog-actualite-comptable/single/mentions-obligatoires-facture
Logiciel de Facturation en Tunisie : Guide Complet pour Votre ..., accessed December 22, 2025, https://www.tassaruf.com/blog/facturation-vente-tunisie.html
Facturation Achat en Tunisie : Processus et Règlement, accessed December 22, 2025, https://www.tassaruf.com/blog/facturation-achat-tunisie.html
Digest de la fiscalité tunisienne : Section 2 - Profiscal, accessed December 22, 2025, http://www.profiscal.com/Impot_en_Tunisie/Digest2.htm
Obligations fiscales en matière de facturation - Facture Tunisie, accessed December 22, 2025, https://facture-tunisie.com/411/fr/9/reglementations/obligations-fiscales-en-matiere-de-facturation
Code des Droits d'Enregistrement et de Timbre 2025 - JIBAYA, accessed December 22, 2025, https://jibaya.tn/docs/code-des-droits-denregistrement-et-de-timbre-2025/
Bulletin officiel des douanes, accessed December 22, 2025, https://www.douane.gouv.fr/sites/default/files/dana/files/BIC_01-137.doc
Numérotation de facture : les règles à suivre - Facture.net, accessed December 22, 2025, https://www.facture.net/blog/regles-de-numerotation-de-facture/
Les arrondis | Ministère de l'Économie des Finances et de la Souveraineté industrielle et énergétique, accessed December 22, 2025, https://www.economie.gouv.fr/dgfip/les-arrondis
Factures : quelles sont les mentions obligatoires ? | CCI Paris Ile-de-France, accessed December 22, 2025, https://www.entreprises.cci-paris-idf.fr/fiches-pratiques/factures-quelles-sont-les-mentions-obligatoires
Principales dispositions de la loi de Finances 2023 - Facture Tunisie, accessed December 22, 2025, https://facture-tunisie.com/412/fr/33/reglementations/principales-dispositions-de-la-loi-de-finances-2023
CODE TVA 2017 FR.pdf - Ministère des Finances, accessed December 22, 2025, https://www.finances.gov.tn/sites/default/files/CODE%20TVA%202017%20FR.pdf
Code de la TVA - Fait Générateur - Tunisie - Jurisite Tunisie, accessed December 22, 2025, https://www.jurisitetunisie.com/tunisie/codes/tva/tva1025.htm
Quel est le fait générateur de la TVA en cas de vente de marchandises (cas des commandes successives)? | Ministère des Finances, accessed December 22, 2025, https://www.finances.gov.tn/fr/node/895
TVA en Tunisie : Champ d'Application et Règles | PDF | Taxe sur la valeur ajoutée - Scribd, accessed December 22, 2025, https://fr.scribd.com/document/535713166/cours-tva
Facturation en Tunisie : les obligations légales - Swiver, accessed December 22, 2025, https://swiver.io/blog/facturation-en-tunisie-les-obligations-legales/
TVA - Ministère des Finances, accessed December 22, 2025, https://www.finances.gov.tn/fr/taxonomy/term/55?page=1
Nouvelles dispositions de la loi de finances 2026 en Tunisie, accessed December 22, 2025, https://facture-tunisie.com/411/fr/42/reglementations/nouvelles-dispositions-de-la-loi-de-finances-2026-en-tunisie
Facturation Électronique en Tunisie : Cadre Légal, Nouveautés 2025 et Opportunités pour les Entreprises - Luca Pacioli, accessed December 22, 2025, https://lucapacioli.com.tn/fr/blog/facturation-%C3%A9lectronique-en-tunisie-cadre-l%C3%A9gal-nouveaut%C3%A9s-2025-et-opportunit%C3%A9s-pour-les-entreprises
La Révolution de la Facture Électronique en Tunisie : Tout savoir sur le système "El Fatoora" de Tunisie TradeNet (TTN) - Swiver, accessed December 22, 2025, https://swiver.io/blog/la-revolution-de-la-facture-electronique-en-tunisie/
